Debug access of eyewear having multiple socs

ABSTRACT

An eyewear device that includes a plurality of SoCs that share processing workload, and a USB port configured to perform low-power debugging and automation of the plurality of SoCs, such as using either a Universal Asynchronous Receiver-Transmitter (UART) or a Serial Wire Debug (SWD). The eyewear includes a USB hub configured such that the USB port can simultaneously communicate with the plurality of SoCs. The USB hub can be shut down to disable the USB hub, and all the SoCs can enter their low-power modes without being kept awake by a persistent USB connection. The eyewear includes a first switch and a control logic, wherein the control logic controls the first switch and enables the USB port to perform low-power debugging and automation of the SoCs. The eyewear further includes a second switch, wherein the control logic controls the second switch to enable the USB port to perform low-power debugging and automation of the SoCs via a processor, or to enable the USB port to control each of the SoCs.

TECHNICAL FIELD

Examples set forth in the present disclosure relate to the field ofelectronic devices and, more particularly, to eyewear devices.

BACKGROUND

Many types of computers and electronic devices available today, such asmobile devices (e.g., smartphones, tablets, and laptops), handhelddevices, and wearable devices (e.g., smart glasses, digital eyewear,headwear, headgear, and head-mounted displays), include a variety ofcameras, sensors, wireless transceivers, input systems (e.g.,touch-sensitive surfaces, pointers), peripheral devices, displays, andgraphical user interfaces (GUIs) through which a user can interact withdisplayed content.

Augmented reality (AR) combines real objects in a physical environmentwith virtual objects and displays the combination to a user. Thecombined display gives the impression that the virtual objects areauthentically present in the environment, especially when the virtualobjects appear and behave like the real objects.

BRIEF DESCRIPTION OF THE DRAWINGS

Features of the various examples described will be readily understoodfrom the following detailed description, in which reference is made tothe figures. A reference numeral is used with each element in thedescription and throughout the several views of the drawing. When aplurality of similar elements is present, a single reference numeral maybe assigned to like elements, with an added letter referring to aspecific element. The letter may be dropped when referring to more thanone of the elements or a non-specific one of the elements.

The various elements shown in the figures are not drawn to scale unlessotherwise indicated. The dimensions of the various elements may beenlarged or reduced in the interest of clarity. The several figuresdepict one or more implementations and are presented by way of exampleonly and should not be construed as limiting. Included in the drawingare the following figures:

FIG. 1A is a side view (right) of an example hardware configuration ofan eyewear device suitable for use in an eyewear system;

FIG. 1B is a perspective, partly sectional view of a right templeportion of the eyewear device of FIG. 1A depicting a right visible-lightcamera, and a circuit board;

FIG. 1C is a side view (left) of an example hardware configuration ofthe eyewear device of FIG. 1A, which shows a left visible-light camera;

FIG. 1D is a perspective, partly sectional view of a left temple portionof the eyewear device of FIG. 1C depicting the left visible-lightcamera, and a circuit board;

FIGS. 2A and 2B are rear views of example hardware configurations of aneyewear device utilized in the eyewear system;

FIG. 2C illustrates detecting eye gaze direction;

FIG. 2D illustrates detecting eye position;

FIG. 3 is a diagrammatic depiction of a three-dimensional scene, a leftraw image captured by a left visible-light camera, and a right raw imagecaptured by a right visible-light camera;

FIG. 4 is a functional block diagram of an example eyewear systemincluding an eyewear device connected to a mobile device and a serversystem via various networks;

FIG. 5 is a diagrammatic representation of an example hardwareconfiguration for a mobile device of the eyewear system of FIG. 4 ;

FIG. 6 is a partial block diagram of an eyewear device with a firstsystem on a chip adjacent one temple and a second system on a chipadjacent the other temple;

FIG. 7 is a flowchart of example steps for performing operations oneyewear with a first system on a chip (SoC) and a second SoC;

FIG. 8 is a block diagram of the eyewear including a universal serialbus (USB) port and a USB hub to provide debug access to the SoCs; and

FIG. 9 is a flowchart of example steps for performing debug operationson the eyewear using the USB port and the USB hub.

DETAILED DESCRIPTION

An eyewear device that includes a plurality of SoCs that shareprocessing workload, and a USB port configured to perform low-powerdebugging (Debug) and automation of the plurality of SoCs, such as usingeither a Universal Asynchronous Receiver-Transmitter (UART) or a SerialWire Debug (SWD). The eyewear includes a USB hub configured such thatthe USB port can simultaneously communicate with the plurality of SoCs.The USB hub can be shut down, and all the SoCs can enter their low-powermodes without being kept awake by a persistent USB connection. Theeyewear includes a first switch and a control logic, wherein the controllogic controls the first switch and enables the USB port to performlow-power debugging and automation of the SoCs. The eyewear furtherincludes a second switch, wherein the control logic controls the secondswitch to enable the USB port to perform low-power debugging andautomation of the SoCs via a processor, or to enable the USB port tocontrol each of the SoCs.

The following detailed description includes systems, methods,techniques, instruction sequences, and computing machine programproducts illustrative of examples set forth in the disclosure. Numerousdetails and examples are included for the purpose of providing athorough understanding of the disclosed subject matter and its relevantteachings. Those skilled in the relevant art, however, may understandhow to apply the relevant teachings without such details. Aspects of thedisclosed subject matter are not limited to the specific devices,systems, and method described because the relevant teachings can beapplied or practice in a variety of ways. The terminology andnomenclature used herein is for the purpose of describing particularaspects only and is not intended to be limiting. In general, well-knowninstruction instances, protocols, structures, and techniques are notnecessarily shown in detail.

The terms “system on a chip” or “SoC” are used herein to refer to anintegrated circuit (also known as a “chip”) that integrates componentsof an electronic system on a single substrate or microchip. Thesecomponents include a central processing unit (CPU), a graphicalprocessing unit (GPU), an image signal processor (ISP), a memorycontroller, a video decoder, and a system bus interface for connectionto another SoC. The components of the SoC may additionally include, byway of non-limiting example, one or more of an interface for an inertialmeasurement unit (IMU; e.g., I2C, SPI, I3C, etc.), a video encoder, atransceiver (TX/RX; e.g., Wi-Fi, Bluetooth®, or a combination thereof),and digital, analog, mixed-signal, and radio frequency signal processingfunctions.

The terms “coupled” or “connected” as used herein refer to any logical,optical, physical, or electrical connection, including a link or thelike by which the electrical or magnetic signals produced or supplied byone system element are imparted to another coupled or connected systemelement. Unless described otherwise, coupled or connected elements ordevices are not necessarily directly connected to one another and may beseparated by intermediate components, elements, or communication media,one or more of which may modify, manipulate, or carry the electricalsignals. The term “on” means directly supported by an element orindirectly supported by the element through another element that isintegrated into or supported by the element.

The term “proximal” is used to describe an item or part of an item thatis situated near, adjacent, or next to an object or person; or that iscloser relative to other parts of the item, which may be described as“distal.” For example, the end of an item nearest an object may bereferred to as the proximal end, whereas the generally opposing end maybe referred to as the distal end.

The orientations of the eyewear device, other mobile devices, associatedcomponents and any other devices incorporating a camera, an inertialmeasurement unit, or both such as shown in any of the drawings, aregiven by way of example only, for illustration and discussion purposes.In operation, the eyewear device may be oriented in any other directionsuitable to the particular application of the eyewear device; forexample, up, down, sideways, or any other orientation. Also, to theextent used herein, any directional term, such as front, rear, inward,outward, toward, left, right, lateral, longitudinal, up, down, upper,lower, top, bottom, side, horizontal, vertical, and diagonal are used byway of example only, and are not limiting as to the direction ororientation of any camera or inertial measurement unit as constructed oras otherwise described herein.

Additional objects, advantages and novel features of the examples willbe set forth in part in the following description, and in part willbecome apparent to those skilled in the art upon examination of thefollowing and the accompanying drawings or may be learned by productionor operation of the examples. The objects and advantages of the presentsubject matter may be realized and attained by means of themethodologies, instrumentalities and combinations particularly pointedout in the appended claims.

Reference now is made in detail to the examples illustrated in theaccompanying drawings and discussed below.

FIG. 1A is a side view (right) of an example hardware configuration ofan eyewear device 100 which includes a touch-sensitive input device ortouchpad 181. As shown, the touchpad 181 may have a boundary that issubtle and not easily seen; alternatively, the boundary may be plainlyvisible or include a raised or otherwise tactile edge that providesfeedback to the user about the location and boundary of the touchpad181. In other implementations, the eyewear device 100 may include atouchpad on the left side.

The surface of the touchpad 181 is configured to detect finger touches,taps, and gestures (e.g., moving touches) for use with a GUI displayedby the eyewear device, on an image display, to allow the user tonavigate through and select menu options in an intuitive manner, whichenhances and simplifies the user experience.

Detection of finger inputs on the touchpad 181 can enable severalfunctions. For example, touching anywhere on the touchpad 181 may causethe GUI to display or highlight an item on the image display, which maybe projected onto at least one of the optical assemblies 180A, 180B.Double tapping on the touchpad 181 may select an item or icon. Slidingor swiping a finger in a particular direction (e.g., from front to back,back to front, up to down, or down to) may cause the items or icons toslide or scroll in a particular direction; for example, to move to anext item, icon, video, image, page, or slide. Sliding the finger inanother direction may slide or scroll in the opposite direction; forexample, to move to a previous item, icon, video, image, page, or slide.The touchpad 181 can be virtually anywhere on the eyewear device 100.

In one example, an identified finger gesture of a single tap on thetouchpad 181, initiates selection or pressing of a graphical userinterface element in the image presented on the image display of theoptical assembly 180A, 180B. An adjustment to the image presented on theimage display of the optical assembly 180A, 180B based on the identifiedfinger gesture can be a primary action which selects or submits thegraphical user interface element on the image display of the opticalassembly 180A, 180B for further display or execution.

As shown in FIG. 1A, the eyewear device 100 includes a rightvisible-light camera 114B. As further described herein, two cameras114A, 114B capture image information for a scene from two separateviewpoints. The two captured images may be used to project athree-dimensional display onto an image display for viewing on or with3D glasses.

The eyewear device 100 includes a right optical assembly 180B with animage display to present images, such as depth images. As shown in FIGS.1A and 1B, the eyewear device 100 includes the right visible-lightcamera 114B. The eyewear device 100 can include multiple visible-lightcameras 114A, 114B that form a passive type of three-dimensional camera,such as stereo camera, of which the right visible-light camera 114B islocated on a right temple portion 110B. As shown in FIGS. 1C-D, theeyewear device 100 also includes a left visible-light camera 114Alocation on a left temple portion 110A.

Left and right visible-light cameras 114A, 114B are sensitive to thevisible-light range wavelength. Each of the visible-light cameras 114A,114B have a different frontward facing field of view which areoverlapping to enable generation of three-dimensional depth images.Right visible-light camera 114B captures a right field of view 111B andleft visible-light camera 114A captures a left field of view 111A.Generally, a “field of view” is the part of the scene that is visiblethrough the camera at a particular position and orientation in space.The fields of view 111A and 111B have an overlapping field of view 304(FIG. 3 ). Objects or object features outside the field of view 111A,111B when the visible-light camera captures the image are not recordedin a raw image (e.g., photograph or picture). The field of viewdescribes an angle range or extent, which the image sensor of thevisible-light camera 114A, 114B picks up electromagnetic radiation of agiven scene in a captured image of the given scene. Field of view can beexpressed as the angular size of the view cone; i.e., an angle of view.The angle of view can be measured horizontally, vertically, ordiagonally.

In an example, visible-light cameras 114A, 114B have a field of viewwith an angle of view between 15° to 30°, for example 24°, and have aresolution of 480×480 pixels or greater. In another example, the fieldof view can be much wider, such as 100° or greater. The “angle ofcoverage” describes the angle range that a lens of visible-light cameras114A, 114B or infrared camera 410 (see FIG. 2A) can effectively image.Typically, the camera lens produces an image circle that is large enoughto cover the film or sensor of the camera completely, possibly includingsome vignetting (e.g., a darkening of the image toward the edges whencompared to the center). If the angle of coverage of the camera lensdoes not fill the sensor, the image circle will be visible, typicallywith strong vignetting toward the edge, and the effective angle of viewwill be limited to the angle of coverage.

Examples of such visible-light cameras 114A, 114B include ahigh-resolution complementary metal-oxide-semiconductor (CMOS) imagesensor and a digital VGA camera (video graphics array) capable ofresolutions of 640p (e.g., 640×480 pixels for a total of 0.3megapixels), 720p, or 1080p. Other examples of visible-light cameras114A, 114B that can capture high-definition (HD) still images and storethem at a resolution of 1642 by 1642 pixels (or greater); or recordhigh-definition video at a high frame rate (e.g., thirty to sixty framesper second or more) and store the recording at a resolution of 1216 by1216 pixels (or greater).

The eyewear device 100 may capture image sensor data from thevisible-light cameras 114A, 114B along with geolocation data, digitizedby an image processor, for storage in a memory. The visible-lightcameras 114A, 114B capture respective left and right raw images in thetwo-dimensional space domain that comprise a matrix of pixels on atwo-dimensional coordinate system that includes an X-axis for horizontalposition and a Y-axis for vertical position. Each pixel includes a colorattribute value (e.g., a red pixel light value, a green pixel lightvalue, or a blue pixel light value); and a position attribute (e.g., anX-axis coordinate and a Y-axis coordinate).

In order to capture stereo images for later display as athree-dimensional projection, an image processor 412 (shown in FIG. 4 )may be coupled to the visible-light cameras 114A, 114B to receive andstore the visual image information. The image processor 412, or anotherprocessor, controls operation of the visible-light cameras 114A, 114B toact as a stereo camera simulating human binocular vision and may add atimestamp to each image. The timestamp on each pair of images allowsdisplay of the images together as part of a three-dimensionalprojection. Three-dimensional projections produce an immersive,life-like experience that is desirable in a variety of contexts,including virtual reality (VR) and video gaming.

FIG. 1B is a perspective, cross-sectional view of a right temple portion110B of the eyewear device 100 of FIG. 1A depicting the rightvisible-light camera 114B of the camera system, and a circuit board.FIG. 1C is a side view (left) of an example hardware configuration of aneyewear device 100 of FIG. 1A, which shows a left visible-light camera114A of the camera system. FIG. 1D is a perspective, cross-sectionalview of a left temple portion 110A of the eyewear device of FIG. 1Cdepicting the left visible-light camera 114A of the three-dimensionalcamera, and a circuit board. Construction and placement of the leftvisible-light camera 114A is substantially similar to the rightvisible-light camera 114B, except the connections and coupling are onthe left lateral side 170A.

As shown in the example of FIG. 1B, the eyewear device 100 includes theright visible-light camera 114B and a circuit board 140B, which may be aflexible printed circuit board (PCB). A right hinge 126B connects theright temple portion 110B to a right temple 125B of the eyewear device100. In some examples, components of the right visible-light camera114B, the flexible PCB 140B, or other electrical connectors or contactsmay be located on the right temple 125B, the right hinge 126B, the righttemple portion 110B, the frame 105, or a combination thereof. Thecomponents (or subset thereof) may be incorporated in an SoC.

As shown in the example of FIG. 1D, the eyewear device 100 includes theleft visible-light camera 114A and a circuit board 140A, which may be aflexible printed circuit board (PCB). A left hinge 126A connects theleft temple portion 110A to a left temple 125A of the eyewear device100. In some examples, components of the left visible-light camera 114A,the flexible PCB 140A, or other electrical connectors or contacts may belocated on the left temple 125A, the left hinge 126A, the left templeportion 110A, the frame 105, or a combination thereof. The components(or subset thereof) may be incorporated in an SoC.

The left temple portion 110A and the right temple portion 110B includestemple portion body 190 and a temple portion cap, with the templeportion cap omitted in the cross-section of FIG. 1B and FIG. 1D.Disposed inside the left temple portion 110A and the right templeportion 110B are various interconnected circuit boards, such as PCBs orflexible PCBs, that include controller circuits for the respective leftvisible-light camera 114A and the right visible-light camera 114B,microphone(s) 130, speaker 132, low-power wireless circuitry (e.g., forwireless short range network communication via Bluetooth™), high-speedwireless circuitry (e.g., for wireless local area network communicationvia Wi-Fi). The components and circuitry (or subset thereof) in eachtemple portion 110 may be incorporated in an SoC.

The right visible-light camera 114B is coupled to or disposed on theflexible PCB 140B and covered by a visible-light camera cover lens,which is aimed through opening(s) formed in the frame 105. For example,the right rim 107B of the frame 105, shown in FIG. 2A, is connected tothe right temple portion 110B and includes the opening(s) for thevisible-light camera cover lens. The frame 105 includes a front sideconfigured to face outward and away from the eye of the user. Theopening for the visible-light camera cover lens is formed on and throughthe front or outward-facing side of the frame 105. In the example, theright visible-light camera 114B has an outward-facing field of view 111B(shown in FIG. 3 ) with a line of sight or perspective that iscorrelated with the right eye of the user of the eyewear device 100. Thevisible-light camera cover lens can also be adhered to a front side oroutward-facing surface of the right temple portion 110B in which anopening is formed with an outward-facing angle of coverage, but in adifferent outwardly direction. The coupling can also be indirect viaintervening components. Although shown as being formed on the circuitboards of the right temple portion 110B, the right visible-light camera114B can be formed on the circuit boards of the left temple 125B or theframe 105.

The left visible-light camera 114A is coupled to or disposed on theflexible PCB 140A and covered by a visible-light camera cover lens,which is aimed through opening(s) formed in the frame 105. For example,the left rim 107A of the frame 105, shown in FIG. 2A, is connected tothe left temple portion 110A and includes the opening(s) for thevisible-light camera cover lens. The frame 105 includes a front sideconfigured to face outward and away from the eye of the user. Theopening for the visible-light camera cover lens is formed on and throughthe front or outward-facing side of the frame 105. In the example, theleft visible-light camera 114A has an outward-facing field of view 111A(shown in FIG. 3 ) with a line of sight or perspective that iscorrelated with the left eye of the user of the eyewear device 100. Thevisible-light camera cover lens can also be adhered to a front side oroutward-facing surface of the left temple portion 110A in which anopening is formed with an outward-facing angle of coverage, but in adifferent outwardly direction. The coupling can also be indirect viaintervening components. Although shown as being formed on the circuitboards of the left temple portion 110A, the left visible-light camera114A can be formed on the circuit boards of the left temple 125A or theframe 105.

FIGS. 2A and 2B are perspective views, from the rear, of examplehardware configurations of the eyewear device 100, including twodifferent types of image displays. The eyewear device 100 is sized andshaped in a form configured for wearing by a user; the form ofeyeglasses is shown in the example. The eyewear device 100 can takeother forms and may incorporate other types of frameworks; for example,a headgear, a headset, or a helmet.

In the eyeglasses example, eyewear device 100 includes a frame 105including a left rim 107A connected to a right rim 107B via a bridge 106adapted to be supported by a nose of the user. The left and right rims107A, 107B include respective apertures 175A, 175B, which hold arespective optical element 180A, 180B, such as a lens and a displaydevice. As used herein, the term “lens” is meant to include transparentor translucent pieces of glass or plastic having curved or flat surfacesthat cause light to converge/diverge or that cause little or noconvergence or divergence.

Although shown as having two optical elements 180A, 180B, the eyeweardevice 100 can include other arrangements, such as a single opticalelement (or it may not include any optical element 180A, 180B),depending on the application or the intended user of the eyewear device100. As further shown, eyewear device 100 includes a left temple portion110A adjacent the left lateral side 170A of the frame 105 and a righttemple portion 110B adjacent the right lateral side 170B of the frame105. The temple portions 110A, 110B may be integrated into the frame 105on the respective lateral sides 170A, 170B (as illustrated) orimplemented as separate components attached to the frame 105 on therespective lateral sides 170A, 170B. Alternatively, the temple portions110A, 110B may be integrated into temples (not shown) attached to theframe 105.

In one example, the image display of optical assembly 180A, 180Bincludes an integrated image display 177. As shown in FIG. 2A, eachoptical assembly 180A, 180B includes a suitable display matrix 177, suchas a liquid crystal display (LCD), an organic light-emitting diode(OLED) display, or any other such display. Each optical assembly 180A,180B also includes an optical layer or layers 176, which can includelenses, optical coatings, prisms, mirrors, waveguides, optical strips,and other optical components in any combination. The optical layers176A, 176B, . . . 176N (shown as 176A-N in FIG. 2A and herein) caninclude a prism having a suitable size and configuration and including afirst surface for receiving light from a display matrix and a secondsurface for emitting light to the eye of the user. The prism of theoptical layers 176A-N extends over all or at least a portion of therespective apertures 175A, 175B formed in the left and right rims 107A,107B to permit the user to see the second surface of the prism when theeye of the user is viewing through the corresponding left and right rims107A, 107B. The first surface of the prism of the optical layers 176A-Nfaces upwardly from the frame 105 and the display matrix 177 overliesthe prism so that photons and light emitted by the display matrix 177impinge the first surface. The prism is sized and shaped so that thelight is refracted within the prism and is directed toward the eye ofthe user by the second surface of the prism of the optical layers176A-N. In this regard, the second surface of the prism of the opticallayers 176A-N can be convex to direct the light toward the center of theeye. The prism can optionally be sized and shaped to magnify the imageprojected by the display matrix 177, and the light travels through theprism so that the image viewed from the second surface is larger in oneor more dimensions than the image emitted from the display matrix 177.

In one example, the optical layers 176A-N may include an LCD layer thatis transparent (keeping the lens open) unless and until a voltage isapplied which makes the layer opaque (closing or blocking the lens). Theimage processor 412 on the eyewear device 100 may execute programming toapply the voltage to the LCD layer in order to produce an active shuttersystem, making the eyewear device 100 suitable for viewing visualcontent when displayed as a three-dimensional projection. Technologiesother than LCD may be used for the active shutter mode, including othertypes of reactive layers that are responsive to a voltage or anothertype of input.

In another example, the image display device of optical assembly 180A,180B includes a projection image display as shown in FIG. 2B. Eachoptical assembly 180A, 180B includes a laser projector 150, which is athree-color laser projector using a scanning mirror or galvanometer.During operation, an optical source such as a laser projector 150 isdisposed in or on one of the temples 125A, 125B of the eyewear device100. Optical assembly 180B in this example includes one or more opticalstrips 155A, 155B, . . . 155N (shown as 155A-N in FIG. 2B) which arespaced apart and across the width of the lens of each optical assembly180A, 180B or across a depth of the lens between the front surface andthe rear surface of the lens.

As the photons projected by the laser projector 150 travel across thelens of each optical assembly 180A, 180B, the photons encounter theoptical strips 155A-N. When a particular photon encounters a particularoptical strip, the photon is either redirected toward the user's eye, orit passes to the next optical strip. A combination of modulation oflaser projector 150, and modulation of optical strips, may controlspecific photons or beams of light. In an example, a processor controlsoptical strips 155A-N by initiating mechanical, acoustic, orelectromagnetic signals. Although shown as having two optical assemblies180A, 180B, the eyewear device 100 can include other arrangements, suchas a single or three optical assemblies, or each optical assembly 180A,180B may have arranged different arrangement depending on theapplication or intended user of the eyewear device 100.

In another example, the eyewear device 100 shown in FIG. 2B may includetwo projectors, a left projector (not shown) and a right projector(shown as projector 150). The left optical assembly 180A may include aleft display matrix (not shown) or a left set of optical strips (notshown) which are configured to interact with light from the leftprojector. In this example, the eyewear device 100 includes a leftdisplay and a right display.

As further shown in FIGS. 2A and 2B, eyewear device 100 includes a lefttemple portion 110A adjacent the left lateral side 170A of the frame 105and a right temple portion 110B adjacent the right lateral side 170B ofthe frame 105. The temple portions 110A, 110B may be integrated into theframe 105 on the respective lateral sides 170A, 170B (as illustrated) orimplemented as separate components attached to the frame 105 on therespective lateral sides 170A, 170B. Alternatively, the temple portions110A, 110B may be integrated into temples 125A, 125B attached to theframe 105.

Referring to FIG. 2A, the frame 105 or one or more of the left and righttemples 110A-B include an infrared emitter 215 and an infrared camera220. The infrared emitter 215 and the infrared camera 220 can beconnected to the flexible PCB 140B by soldering, for example. Otherarrangements of the infrared emitter 215 and infrared camera 220 can beimplemented, including arrangements in which the infrared emitter 215and infrared camera 220 are both on the right rim 107B, or in differentlocations on the frame 105, for example, the infrared emitter 215 is onthe left rim 107A and the infrared camera 220 is on the right rim 107B.In another example, the infrared emitter 215 is on the frame 105 and theinfrared camera 220 is on one of the temples 110A-B, or vice versa. Theinfrared emitter 215 can be connected essentially anywhere on the frame105, left temple 110A, or right temple 110B to emit a pattern ofinfrared light. Similarly, the infrared camera 220 can be connectedessentially anywhere on the frame 105, left temple 110A, or right temple110B to capture at least one reflection variation in the emitted patternof infrared light.

The infrared emitter 215 and infrared camera 220 are arranged to faceinwards towards an eye of the user with a partial or full field of viewof the eye in order to identify the respective eye position and gazedirection. For example, the infrared emitter 215 and infrared camera 220are positioned directly in front of the eye, in the upper part of theframe 105 or in the temples 110A-B at either ends of the frame 105.

In an example, the processor 432 utilizes eye tracker 213 to determinean eye gaze direction 230 of a wearer's eye 234 as shown in FIG. 2C, andan eye position 236 of the wearer's eye 234 within an eyebox as shown inFIG. 2D. In one example, the eye tracker 213 is a scanner which usesinfrared light illumination (e.g., near-infrared, short-wavelengthinfrared, mid-wavelength infrared, long-wavelength infrared, or farinfrared) to capture image of reflection variations of infrared lightfrom the eye 234 to determine the gaze direction 230 of a pupil 232 ofthe eye 234, and also the eye position 236 with respect to the display180D.

FIG. 3 is a diagrammatic depiction of a three-dimensional scene 306, aleft raw image 302A captured by a left visible-light camera 114A, and aright raw image 302B captured by a right visible-light camera 114B. Theleft field of view 111A may overlap, as shown, with the right field ofview 111B. The overlapping field of view 304 represents that portion ofthe image captured by both cameras 114A, 114B. The term ‘overlapping’when referring to field of view means the matrix of pixels in thegenerated raw images overlap by thirty percent (30%) or more.‘Substantially overlapping’ means the matrix of pixels in the generatedraw images—or in the infrared image of scene—overlap by fifty percent(50%) or more. As described herein, the two raw images 302A, 302B may beprocessed to include a timestamp, which allows the images to bedisplayed together as part of a three-dimensional projection.

For the capture of stereo images, as illustrated in FIG. 3 , a pair ofraw red, green, and blue (RGB) images are captured of a real scene 306at a given moment in time—a left raw image 302A captured by the leftcamera 114A and right raw image 302B captured by the right camera 114B.When the pair of raw images 302A, 302B are processed (e.g., by the imageprocessor 412), depth images are generated. The generated depth imagesmay be viewed on an optical assembly 180A, 180B of an eyewear device, onanother display (e.g., the image display 580 on a mobile device 401), oron a screen.

The generated depth images are in the three-dimensional space domain andcan comprise a matrix of vertices on a three-dimensional locationcoordinate system that includes an X axis for horizontal position (e.g.,length), a Y axis for vertical position (e.g., height), and a Z axis fordepth (e.g., distance). Each vertex may include a color attribute (e.g.,a red pixel light value, a green pixel light value, or a blue pixellight value); a position attribute (e.g., an X location coordinate, a Ylocation coordinate, and a Z location coordinate); a texture attribute;a reflectance attribute; or a combination thereof. The texture attributequantifies the perceived texture of the depth image, such as the spatialarrangement of color or intensities in a region of vertices of the depthimage.

In one example, an eyewear system 400 (FIG. 4 ) includes the eyeweardevice 100, which includes a frame 105, a left temple 110A extendingfrom a left lateral side 170A of the frame 105, and a right temple 125Bextending from a right lateral side 170B of the frame 105. The eyeweardevice 100 may further include at least two visible-light cameras 114A,114B having overlapping fields of view. In one example, the eyeweardevice 100 includes a left visible-light camera 114A with a left fieldof view 111A, as illustrated in FIG. 3 . The left camera 114A isconnected to the frame 105, left temple 125A, or left temple portion110A to capture a left raw image 302A from the left side of scene 306.The eyewear device 100 further includes a right visible-light camera114B with a right field of view 111B. The right camera 114B is connectedto the frame 105, right temple 125B, or right temple portion 110B tocapture a right raw image 302B from the right side of scene 306.

FIG. 4 is a functional block diagram of an example eyewear system 400that includes a wearable device (e.g., an eyewear device 100), a mobiledevice 401, and a server system 498 connected via various networks 495such as the Internet. The eyewear system 400 includes a low-powerwireless connection 425 and a high-speed wireless connection 437 betweenthe eyewear device 100 and the mobile device 401.

As shown in FIG. 4 , the eyewear device 100 includes one or morevisible-light cameras 114A, 114B that capture still images, videoimages, or both still and video images, as described herein. The cameras114A, 114B may have a direct memory access (DMA) to high-speed circuitry430 and function as a stereo camera. The cameras 114A, 114B may be usedto capture initial-depth images that may be rendered intothree-dimensional (3D) models that are texture-mapped images of a red,green, and blue (RGB) imaged scene.

The eyewear device 100 further includes two optical assemblies 180A,180B (one associated with the left lateral side 170A and one associatedwith the right lateral side 170B). The eyewear device 100 also includesan image display driver 442, an image processor 412, low-power circuitry420, and high-speed circuitry 430 (all of which may be duplicated andincorporated into a pair of SoCs). The image displays 177 of eachoptical assembly 180A, 180B are for presenting images, including stillimages, video images, or still and video images. The image displaydriver 442 is coupled to the image displays of each optical assembly180A, 180B in order to control the display of images.

The eyewear device 100 additionally includes one or more microphones 130and speakers 132 (e.g., one of each associated with the left side of theeyewear device and another associated with the right side of the eyeweardevice). The microphones 130 and speakers 132 may be incorporated intothe frame 105, temples 125, or temple portions 110 of the eyewear device100. The one or more speakers 132 are driven by audio processor 443(which may be duplicated and incorporated into a pair of SoCs) undercontrol of low-power circuitry 420, high-speed circuitry 430, or both.The speakers 132 are for presenting audio signals including, forexample, a beat track. The audio processor 443 is coupled to thespeakers 132 in order to control the presentation of sound.

The components shown in FIG. 4 for the eyewear device 100 are located onone or more circuit boards, for example a printed circuit board (PCB) orflexible printed circuit (FPC), located in the rims or temples.Alternatively, or additionally, the depicted components can be locatedin the temple portions, frames, hinges, or bridge of the eyewear device100. Left and right visible-light cameras 114A, 114B can include digitalcamera elements such as a complementary metal-oxide-semiconductor (CMOS)image sensor, a charge-coupled device, a lens, or any other respectivevisible or light capturing elements that may be used to capture data,including still images or video of scenes with unknown objects.

As shown in FIG. 4 , high-speed circuitry 430 includes a high-speedprocessor 432, a memory 434, and high-speed wireless circuitry 436. Inthe example, the image display driver 442 is coupled to the high-speedcircuitry 430 and operated by the high-speed processor 432 in order todrive the left and right image displays of each optical assembly 180A,180B. High-speed processor 432 may be any processor capable of managinghigh-speed communications and operation of any general computing systemneeded for eyewear device 100. High-speed processor 432 includesprocessing resources needed for managing high-speed data transfers onhigh-speed wireless connection 437 to a wireless local area network(WLAN) using high-speed wireless circuitry 436.

In some examples, the high-speed processor 432 executes an operatingsystem such as a LINUX operating system or other such operating systemof the eyewear device 100 and the operating system is stored in memory434 for execution. In addition to any other responsibilities, thehigh-speed processor 432 executes a software architecture for theeyewear device 100 that is used to manage data transfers with high-speedwireless circuitry 436. In some examples, high-speed wireless circuitry436 is configured to implement Institute of Electrical and ElectronicEngineers (IEEE) 802.11 communication standards, also referred to hereinas Wi-Fi. In other examples, other high-speed communications standardsmay be implemented by high-speed wireless circuitry 436.

The low-power circuitry 420 includes a low-power processor 422 andlow-power wireless circuitry 424. The low-power wireless circuitry 424and the high-speed wireless circuitry 436 of the eyewear device 100 caninclude short-range transceivers (Bluetooth™ or Bluetooth Low-Energy(BLE)) and wireless wide, local, or wide-area network transceivers(e.g., cellular or Wi-Fi). Mobile device 401, including the transceiverscommunicating via the low-power wireless connection 425 and thehigh-speed wireless connection 437, may be implemented using details ofthe architecture of the eyewear device 100, as can other elements of thenetwork 495.

Memory 434 includes any storage device capable of storing various dataand applications, including, among other things, camera data generatedby the left and right visible-light cameras 114A, 114B, the infraredcamera(s) 220, the image processor 412, and images generated for display177 by the image display driver 442 on the image display of each opticalassembly 180A, 180B. Although the memory 434 is shown as integrated withhigh-speed circuitry 430, the memory 434 in other examples may be anindependent, standalone element of the eyewear device 100. In certainsuch examples, electrical routing lines may provide a connection througha chip that includes the high-speed processor 432 from the imageprocessor 412 or low-power processor 422 to the memory 434. In otherexamples, the high-speed processor 432 may manage addressing of memory434 such that the low-power processor 422 will boot the high-speedprocessor 432 any time that a read or write operation involving memory434 is needed.

As shown in FIG. 4 , the high-speed processor 432 of the eyewear device100 can be coupled to the camera system (visible-light cameras 114A,114B), the image display driver 442, the user input device 491, and thememory 434. As shown in FIG. 5 , the CPU 530 of the mobile device 401may be coupled to a camera system 570, a mobile display driver 582, auser input layer 591, and a memory 540A.

The server system 498 may be one or more computing devices as part of aservice or network computing system, for example, that include aprocessor, a memory, and network communication interface to communicateover the network 495 with one or more eyewear devices 100 and a mobiledevice 401.

The output components of the eyewear device 100 include visual elements,such as the left and right image displays associated with each lens oroptical assembly 180A, 180B as described in FIGS. 2A and 2B (e.g., adisplay such as a liquid crystal display (LCD), a plasma display panel(PDP), a light emitting diode (LED) display, a projector, or awaveguide). The eyewear device 100 may include a user-facing indicator(e.g., an LED, a loudspeaker, or a vibrating actuator), or anoutward-facing signal (e.g., an LED, a loudspeaker). The image displaysof each optical assembly 180A, 180B are driven by the image displaydriver 442. In some example configurations, the output components of theeyewear device 100 further include additional indicators such as audibleelements (e.g., loudspeakers), tactile components (e.g., an actuatorsuch as a vibratory motor to generate haptic feedback), and other signalgenerators. For example, the device 100 may include a user-facing set ofindicators, and an outward-facing set of signals. The user-facing set ofindicators are configured to be seen or otherwise sensed by the user ofthe device 100. For example, the device 100 may include an LED displaypositioned so the user can see it, a one or more speakers positioned togenerate a sound the user can hear, or an actuator to provide hapticfeedback the user can feel. The outward-facing set of signals areconfigured to be seen or otherwise sensed by an observer near the device100. Similarly, the device 100 may include an LED, a loudspeaker, or anactuator that is configured and positioned to be sensed by an observer.

The input components of the eyewear device 100 may include inputcomponents (e.g., a touch screen or touchpad 181 configured to receivealphanumeric input, a photo-optical keyboard, or otheralphanumeric-configured elements), pointer-based input components (e.g.,a mouse, a touchpad, a trackball, a joystick, a motion sensor, or otherpointing instruments), tactile input components (e.g., a button switch,a touch screen or touchpad that senses the location, force or locationand force of touches or touch gestures, or other tactile-configuredelements), and audio input components (e.g., a microphone), and thelike. The mobile device 401 and the server system 498 may includealphanumeric, pointer-based, tactile, audio, and other input components.

In some examples, the eyewear device 100 includes a collection ofmotion-sensing components referred to as an inertial measurement unit472 (which may be duplicated and incorporated into a pair of SoCs). Themotion-sensing components may be micro-electro-mechanical systems (MEMS)with microscopic moving parts, often small enough to be part of amicrochip. The inertial measurement unit (IMU) 472 in some exampleconfigurations includes an accelerometer, a gyroscope, and amagnetometer. The accelerometer senses the linear acceleration of thedevice 100 (including the acceleration due to gravity) relative to threeorthogonal axes (x, y, z). The gyroscope senses the angular velocity ofthe device 100 about three axes of rotation (pitch, roll, yaw).Together, the accelerometer and gyroscope can provide position,orientation, and motion data about the device relative to six axes (x,y, z, pitch, roll, yaw). The magnetometer, if present, senses theheading of the device 100 relative to magnetic north. The position ofthe device 100 may be determined by location sensors, such as a GPS unit473, one or more transceivers to generate relative position coordinates,altitude sensors or barometers, and other orientation sensors (which maybe duplicated and incorporated into a pair of SoCs). Such positioningsystem coordinates can also be received over the wireless connections425, 437 from the mobile device 401 via the low-power wireless circuitry424 or the high-speed wireless circuitry 436.

The IMU 472 may include or cooperate with a digital motion processor orprogramming that gathers the raw data from the components and compute anumber of useful values about the position, orientation, and motion ofthe device 100. For example, the acceleration data gathered from theaccelerometer can be integrated to obtain the velocity relative to eachaxis (x, y, z); and integrated again to obtain the position of thedevice 100 (in linear coordinates, x, y, and z). The angular velocitydata from the gyroscope can be integrated to obtain the position of thedevice 100 (in spherical coordinates). The programming for computingthese useful values may be stored in memory 434 and executed by thehigh-speed processor 432 of the eyewear device 100.

The eyewear device 100 may optionally include additional peripheralsensors, such as biometric sensors, specialty sensors, or displayelements integrated with eyewear device 100. For example, peripheraldevice elements may include any I/O components including outputcomponents, motion components, position components, or any other suchelements described herein. For example, the biometric sensors mayinclude components to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), tomeasure bio signals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), or to identify a person (e.g.,identification based on voice, retina, facial characteristics,fingerprints, or electrical bio signals such as electroencephalogramdata), and the like.

The mobile device 401 may be a smartphone, tablet, laptop computer,access point, or any other such device capable of connecting witheyewear device 100 using both a low-power wireless connection 425 and ahigh-speed wireless connection 437. Mobile device 401 is connected toserver system 498 and network 495. The network 495 may include anycombination of wired and wireless connections.

The eyewear system 400, as shown in FIG. 4 , includes a computingdevice, such as mobile device 401, coupled to an eyewear device 100 overa network 495. The eyewear system 400 includes a memory for storinginstructions and a processor for executing the instructions. Executionof the instructions of the eyewear system 400 by the processor 432configures the eyewear device 100 to cooperate with the mobile device401, and also with another eyewear device 100 over the network 495. Theeyewear system 400 may utilize the memory 434 of the eyewear device 100or the memory elements 540A, 540B, 540C of the mobile device 401 (FIG. 5).

Any of the functionality described herein for the eyewear device 100,the mobile device 401, and the server system 498 can be embodied in oneor more computer software applications or sets of programminginstructions, as described herein. According to some examples,“function,” “functions,” “application,” “applications,” “instruction,”“instructions,” or “programming” are program(s) that execute functionsdefined in the programs. Various programming languages can be employedto develop one or more of the applications, structured in a variety ofmanners, such as object-oriented programming languages (e.g.,Objective-C, Java, or C++) or procedural programming languages (e.g., Cor assembly language). In a specific example, a third-party application(e.g., an application developed using the ANDROID™ or IOS™ softwaredevelopment kit (SDK) by an entity other than the vendor of theparticular platform) may include mobile software running on a mobileoperating system such as IOS™, ANDROID™, WINDOWS® Phone, or anothermobile operating system. In this example, the third-party applicationcan invoke API calls provided by the operating system to facilitatefunctionality described herein.

Hence, a machine-readable medium may take many forms of tangible storagemedium. Non-volatile storage media include, for example, optical ormagnetic disks, such as any of the storage devices in any computerdevices or the like, such as may be used to implement the client device,media gateway, transcoder, etc. shown in the drawings. Volatile storagemedia include dynamic memory, such as main memory of such a computerplatform. Tangible transmission media include coaxial cables; copperwire and fiber optics, including the wires that comprise a bus within acomputer system. Carrier-wave transmission media may take the form ofelectric or electromagnetic signals, or acoustic or light waves such asthose generated during radio frequency (RF) and infrared (IR) datacommunications. Common forms of computer-readable media thereforeinclude for example: a floppy disk, a flexible disk, hard disk, magnetictape, any other magnetic medium, a CD-ROM, DVD or DVD-ROM, any otheroptical medium, punch cards paper tape, any other physical storagemedium with patterns of holes, a RAM, a PROM and EPROM, a FLASH-EPROM,any other memory chip or cartridge, a carrier wave transporting data orinstructions, cables or links transporting such a carrier wave, or anyother medium from which a computer may read programming code or data.Many of these forms of computer readable media may be involved incarrying one or more sequences of one or more instructions to aprocessor for execution.

FIG. 5 is a high-level functional block diagram of an example mobiledevice 401. Mobile device 401 includes a flash memory 540A which storesprogramming to be executed by the CPU 530 to perform all or a subset ofthe functions described herein.

The mobile device 401 may include a camera 570 that comprises at leasttwo visible-light cameras (first and second visible-light cameras withoverlapping fields of view) or at least one visible-light camera and adepth sensor with substantially overlapping fields of view. Flash memory540A may further include multiple images or video, which are generatedvia the camera 570.

As shown, the mobile device 401 includes an image display 580, a mobiledisplay driver 582 to drive the image display 580, and a displaycontroller 584 to control the image display 580. In the example of FIG.5 , the image display 580 includes a user input layer 591 (e.g., atouchscreen) that is layered on top of or otherwise integrated into thescreen used by the image display 580.

Examples of touchscreen-type mobile devices that may be used include(but are not limited to) a smart phone, a personal digital assistant(PDA), a tablet computer, a laptop computer, or other portable device.However, the structure and operation of the touchscreen-type devices isprovided by way of example; the subject technology as described hereinis not intended to be limited thereto. For purposes of this discussion,FIG. 5 therefore provides a block diagram illustration of the examplemobile device 401 with a user interface that includes a touchscreeninput layer 591 for receiving input (by touch, multi-touch, or gesture,and the like, by hand, stylus, or other tool) and an image display 580for displaying content

As shown in FIG. 5 , the mobile device 401 includes at least one digitaltransceiver (XCVR) 510, shown as WWAN XCVRs, for digital wirelesscommunications via a wide-area wireless mobile communication network.The mobile device 401 also includes additional digital or analogtransceivers, such as short-range transceivers (XCVRs) 520 forshort-range network communication, such as via NFC, VLC, DECT, ZigBee,Bluetooth™, or Wi-Fi. For example, short range XCVRs 520 may take theform of any available two-way wireless local area network (WLAN)transceiver of a type that is compatible with one or more standardprotocols of communication implemented in wireless local area networks,such as one of the Wi-Fi standards under IEEE 802.11.

To generate location coordinates for positioning of the mobile device401, the mobile device 401 can include a global positioning system (GPS)receiver. Alternatively, or additionally the mobile device 401 canutilize either or both the short range XCVRs 520 and WWAN XCVRs 510 forgenerating location coordinates for positioning. For example, cellularnetwork, Wi-Fi, or Bluetooth™ based positioning systems can generatevery accurate location coordinates, particularly when used incombination. Such location coordinates can be transmitted to the eyeweardevice over one or more network connections via XCVRs 510, 520.

The transceivers 510, 520 (i.e., the network communication interface)conforms to one or more of the various digital wireless communicationstandards utilized by modern mobile networks. Examples of WWANtransceivers 510 include (but are not limited to) transceiversconfigured to operate in accordance with Code Division Multiple Access(CDMA) and 3rd Generation Partnership Project (3GPP) networktechnologies including, for example and without limitation, 3GPP type 2(or 3GPP2) and LTE, at times referred to as “4G.” For example, thetransceivers 510, 520 provide two-way wireless communication ofinformation including digitized audio signals, still image and videosignals, web page information for display as well as web-related inputs,and various types of mobile message communications to/from the mobiledevice 401.

The mobile device 401 further includes a microprocessor that functionsas a central processing unit (CPU) 530. A processor is a circuit havingelements structured and arranged to perform one or more processingfunctions, typically various data processing functions. Althoughdiscrete logic components could be used, the examples utilize componentsforming a programmable CPU. A microprocessor for example includes one ormore integrated circuit (IC) chips incorporating the electronic elementsto perform the functions of the CPU. The CPU 530, for example, may bebased on any known or available microprocessor architecture, such as aReduced Instruction Set Computing (RISC) using an ARM architecture, ascommonly used today in mobile devices and other portable electronicdevices. Of course, other arrangements of processor circuitry may beused to form the CPU 530 or processor hardware in smartphone, laptopcomputer, and tablet.

The CPU 530 serves as a programmable host controller for the mobiledevice 401 by configuring the mobile device 401 to perform variousoperations, for example, in accordance with instructions or programmingexecutable by CPU 530. For example, such operations may include variousgeneral operations of the mobile device, as well as operations relatedto the programming for applications on the mobile device. Although aprocessor may be configured by use of hardwired logic, typicalprocessors in mobile devices are general processing circuits configuredby execution of programming.

The mobile device 401 includes a memory or storage system, for storingprogramming and data. In the example, the memory system may include aflash memory 540A, a random-access memory (RAM) 540B, and other memorycomponents 540C, as needed. The RAM 540B serves as short-term storagefor instructions and data being handled by the CPU 530, e.g., as aworking data processing memory. The flash memory 540A typically provideslonger-term storage.

Hence, in the example of mobile device 401, the flash memory 540A isused to store programming or instructions for execution by the CPU 530.Depending on the type of device, the mobile device 401 stores and runs amobile operating system through which specific applications areexecuted. Examples of mobile operating systems include Google Android,Apple iOS (for iPhone or iPad devices), Windows Mobile, Amazon Fire OS,RIM BlackBerry OS, or the like.

The processor 432 within the eyewear device 100 may construct a map ofthe environment surrounding the eyewear device 100, determine a locationof the eyewear device within the mapped environment, and determine arelative position of the eyewear device to one or more objects in themapped environment. The processor 432 may construct the map anddetermine location and position information using a simultaneouslocalization and mapping (SLAM) algorithm applied to data received fromone or more sensors. In the context of augmented reality, a SLAMalgorithm is used to construct and update a map of an environment, whilesimultaneously tracking and updating the location of a device (or auser) within the mapped environment. The mathematical solution can beapproximated using various statistical methods, such as particlefilters, Kalman filters, extended Kalman filters, and covarianceintersection.

Sensor data includes images received from one or both of the cameras114A, 114B, distance(s) received from a laser range finder, positioninformation received from a GPS unit 473, or a combination of two ormore of such sensor data, or from other sensors providing data useful indetermining positional information.

FIG. 6 is a partial block diagram of an eyewear device 100 incorporatinga first SoC 602A and a second SoC 602B in accordance with one example.The first SoC 602A is positioned within a left temple portion 110A alongwith a memory 604A (e.g., flash memory), a battery 606A, an IMU 472A, acamera 114A, and display components 608A. The second SoC 602B ispositioned within a right temple portion 110B along with a memory 604B(e.g., flash memory), a battery 606B, an IMU 472B, a camera 114B, anddisplay components 608B. The first SoC 602A is coupled to the second SoCfor communications there between.

Although illustrated in the left temple portion 110A, one or more of thefirst SoC 602A, memory 604A, battery 606A, and display components 608Amay be positioned in the frame 105 adjacent the left temple portion 110A(i.e., on the left lateral side 170A) or in the temple 125A.Additionally, although illustrated in the right temple portion 110B, oneor more of the second SoC 602B, memory 604B, battery 606B, and displaycomponents 608B may be positioned in the frame 105 adjacent the righttemple portion 110B (i.e., on the right lateral side 170B) or the temple125B. Furthermore, although two memories 604A, B, batteries 606A, B, anddisplay components 608A, B are illustrated, fewer or more memories,batteries, and display components may be incorporated. For example, asingle battery 606 may power both SoCs 602A, B and SoCs 602A, B mayaccess three or more memories 604 for performing various operations.

In one example, both SoCs 602 incorporate the same or substantiallysimilar components and component layouts. Thus, their total processingresources are equivalent. In accordance with this example, the first SoC602A is at least substantially identical to the second SoC (i.e., theyare identical or have on overlap is components or processing resourcesof 95% or greater). Through the use of dual SoCs 602 (one positioned onone side of the eyewear device 100 and the other on the other side ofthe eyewear device) cooling is effectively distributed throughout theeyewear device 100 with one side of the eyewear device providing passivecooling for one SoC 602 and the other side of the eyewear deviceproviding passive cooling for the other SoC 602.

In one example, the eyewear device 100 has a thermal passive coolingcapacity per temple of approximately 3 Watts. The display 608 on eachside (e.g., a projection LED display) utilizes approximately 1-2 Watts.Each SoC 602 is designed to operate at less than approximately 1.5 Watts(e.g., 800-1000 mW; unlike the approximately 5 Watts typically used foran SoC in a mobile phone), which enables suitable cooling of theelectronics on each side of the eyewear device 105 utilizing passivecooling through the frame 105, temple portions 110A, temples 125A, or acombination thereof. By incorporating two SoCs 602 (positioned onopposite sides of the eyewear device 100 to take advantage of the uniquepassive cooling capacity presented by the eyewear device 100),computational power meeting or exceeding that available in aconventional mobile device (which utilizes an SoC operating at 5 Wattsof power dissipated) is achievable.

Incorporating the same or similar components and component layouts ineach SoC, enables flexibility in distributing processing workloadbetween the two SoCs 602. In one example, processing workload isdistributed based on adjacent components. In accordance with thisexample, each SoC may drive a respective camera and a display, which maybe desirable from an electrical standpoint.

In another example, processing workload is distributed based onfunctionality. In accordance with this example, one SoC 602 may act as asensor hub (e.g., do all computer vision, CV, and machine learning, ML,processing plus video encoding) and the other SoC 602 may runapplication logic, audio and video rendering functions, andcommunications (e.g., Wi-Fi, Bluetooth®, 4G/5G, etc.). Distributingprocessing workload based on functionality may be desirable from aprivacy perspective. For example, processing sensor information with oneSoC and Wi-Fi with the other enables an implementation where privatedata such as camera images may be prevented from leaving the eyeweardevice unnoticed by not allowing such sensor information to be sent fromthe SoC doing sensor processing to the SoC managing communications. Inanother example, as descripted in further detail below, processingworkload can be shifted based on processing workload (e.g., determinedby SoC temperature or instructions per second).

FIG. 7 is a flowchart 700 for implementing dual SoCs in an eyeweardevice. Although the steps are described with reference to eyeweardevice 100, other suitable eyewear devices in which one or more steps ofthe flowchart 700 can be practiced will be understood by one of skill inthe art from the description herein. Additionally, it is contemplatedthat one or more of the steps shown in FIG. 7 , and described herein maybe omitted, performed simultaneously or in series, performed in an orderother than illustrated and described, or performed in conjunction withadditional steps.

FIG. 7 is a flowchart 700 of example steps for performing operations oneyewear with a first system on a chip and a second system on a chip. Atblock 702, a first SoC (e.g., SoC 602A) performs a first set ofoperations. This includes operating the OS, the first color camera 114A,the second color camera 114B, the first display 608A, and the seconddisplay 608B.

At block 704, a second SoC (e.g., SoC 602B) perform a second set ofoperations. This includes running the CV algorithms, Visual odometry(VIO), tracking hand gestures of the user, and providing depth fromstereo.

At block 706, the eyewear device 100 monitors temperatures of the firstand second SoCs. In one example, each SoC includes an integratedthermistor for measuring temperature. Each SoC may monitor its owntemperature via a respective integrated thermistor and may monitor thetemperature of the other SoC by periodically requesting temperaturereadings from the other SoC.

At block 708, the eyewear device 100 shifts processing workloads betweenthe first and second sets of operations performed on respective SoC tobalance temperature (which effective distributes processing workload).In examples including a primary SoC and a replica SoC, the primary SoCmanages the assignments of workloads to itself and to the replica SoC tomaintain a relatively even distribution between the SoCs. In oneexample, when one of the SoC has a temperature that is above 10% of thetemperature of the other SoC, the primary SoC reallocates processingworkload from the SoC with the higher temperature to the SoC with thelower temperature until the temperature different is less than 5%.Processing instructions performed by each of the SoC may be assignedassignability values from 1 to 10 with 1 never being assignable and 10always being assignable. When shifting processing workloads, the primarySoC initially shifts instructions with assignability values of 10, then9, 8, etc. The steps for blocks 706 and 708 are continuously repeated tomaintain even thermal distribution.

Debug access provides access to low-level interfaces that the end-userwill not typically need. When the eyewear device 100 is worn by theend-user, only wireless protocols, such as Bluetooth™ and Wi-Fi, areneeded to interface with other devices; and wired interfaces, such as aUSB, a Universal Asynchronous Receiver-Transmitter (UART), and a SerialWire Debug (SWD) are disconnected or disabled.

During development and manufacturing, engineering and factory teamsrequire debug access to the eyewear device 100. Debug access providesthe ability to reflash devices with development or debug builds of thefirmware, the ability to recover (unbrick) devices that no longer boot,the ability to monitor serial logs during early boot to debug issues,and the ability to run reliable automated testing on form-factordevices.

On a single SoC eyewear device, most of the debug access is providedthrough a single USB data connection. With eyewear device 100 havingmultiple SoCs 602, the debug access becomes challenging. A safe andsecure method to access all of the SoCs debug interfaces requirescircuitry that is safe from electrostatic discharge (ESD), overvoltage,water ingress, that is invisible to the end user, is USB compliant, thatcan be disabled at the end of a factory line so that the end-user doesnot have debug access, and functional even when all SoC software is inan unknown state.

Adding a separate USB port for each SoC 602 negatively impacts productdesign as it requires extra USB ports that the end user never uses, andit degrades reliability by including additional ingress points formoisture, ESD, and overvoltage. The use of USB switches to select theSoC allows access to only one SoC at a time, and the switches need ahardware mechanism for selecting which SoC to address. Using extra USB-Cdata lanes requires custom hardware for engineers and factory to accessdebug circuits, and they need additional overvoltage protection and ESDprotection. An always-on USB hub increases power consumption whichimpacts thermal performance.

According to this disclosure, as shown in FIG. 8 , a network of analogswitches SW1 and SW2 are controlled to decide where a single USB-C Port802 having data lines 804 are connected. By default, the USB-C Port 802is connected to the main application SoC 602A via switches SW1 and SW2,as shown.

A low-power debug microcontroller unit (MCU) 806 acts as a USB interfacebridge to enable the USB-C Port 802 to selectively access low-speednon-USB interfaces 808 of the SoCs, such as a UART, a SWD, etc., and tocommunicate with all of the SoCs 602A, 602B, and 602C. More than threeSoCs can accessed by the USB-C Port 802 using the debug MCU 806 ifdesired.

A Debug Mode can be enabled when a switch and hub control logic 810toggles switch SW1 and enables a USB Hub 812. This Debug Mode providessimultaneous access of the USB-C Port 802 to all SoCs' USB, UART, andSWD buses 808. This allows the USB-C Port 802 to provide simultaneouslow-power debugging and automation of all SoCs 602A, 602B and 602C. TheDebug Mode can be enabled with software, such as using a DEBUG_EN signalfrom an SoC, shown as SoC 602A, or by a USB-C controller 814 providingdevice test system (DTS) detection to the switch and hub control logic810 when a special cable is connected. This DTS detection allows fullrecovery using the USB-C Port 802 even when the SOC software is in a badstate.

The second switch SW2 is also controlled by the switch and hub controllogic 810 to selectively connect the USB-C Port 802 directly to thedebug MCU 806 while the rest of the USB Hub 812 ports are disabled. Thisallows the USB-C Port 802 to provide simultaneous low-power debuggingand automation of all SoCs 602A, 602B and 602C. The USB Hub 812 is shutdown by the switch and hub control logic 810 to disable the USB Hub 812ports, and all the SoCs 602A, 602B and 602C 602 can enter theirlow-power modes without being kept awake by a persistent USB connection.The software DEBUG_EN signal and the USB-C controller 814 DTS detectioncan both be disabled with non-volatile memory (NVM) writes at the end ofthe factory line to permanently disable the Debug Mode for end users.

Referring to FIG. 9 , there is shown a flowchart 900 of example stepsfor performing debug operations on eyewear device 100 having multipleSoCs.

At block 902, the switch and hub control logic 810 toggles switch SW1 toenable the USB-C Port 802 to enter the Debug Mode. This Debug Modeprovides simultaneous access of the USB-C Port 802 to all SoCs' USB,UART, and SWD buses 808. This allows the USB-C Port 802 to providesimultaneous low-power debugging and automation of all SoCs 602A, 602Band 602C. The Debug Mode can be enabled with software, such as using aDEBUG_EN signal from an SoC, shown as SoC 602A, or by the USB-Ccontroller 814 providing a DTS detection to the switch and hub controllogic 810 when a special cable is connected.

At block 904, the USB-C Port 802 simultaneously accesses all SoCs' USB,UART, and SWD buses 808. The Debug Mode can be enabled with software,such as using the DEBUG_EN signal from an SoC, shown as SoC 602A, or bythe USB-C controller 814 providing the DTS detection to the switch andhub control logic 810 when a special cable is connected.

At block 906, the switch and hub control logic 810 switches the secondswitch SW2 such that the USB-C Port 802 is directly connected to thedebug MCU 806 while the rest of the USB Hub 812 ports are disabled. Thisallows for low-power debugging and automation of the SoCs. The USB Hub812 shuts down and all the SOCs 602 to enter their low-power modeswithout being kept awake by a persistent USB connection.

The use of the MIPI interface bridge is discussed in relation to usebetween to SoCs in eyewear, however, this bridge can be used betweenother circuits in other devices if desired.

Except as stated immediately above, nothing that has been stated orillustrated is intended or should be interpreted to cause a dedicationof any component, step, feature, object, benefit, advantage, orequivalent to the public, regardless of whether it is or is not recitedin the claims.

It will be understood that the terms and expressions used herein havethe ordinary meaning as is accorded to such terms and expressions withrespect to their corresponding respective areas of inquiry and studyexcept where specific meanings have otherwise been set forth herein.Relational terms such as first and second and the like may be usedsolely to distinguish one entity or action from another withoutnecessarily requiring or implying any actual such relationship or orderbetween such entities or actions. The terms “comprises,” “comprising,”“includes,” “including,” or any other variation thereof, are intended tocover a non-exclusive inclusion, such that a process, method, article,or apparatus that comprises or includes a list of elements or steps doesnot include only those elements or steps but may include other elementsor steps not expressly listed or inherent to such process, method,article, or apparatus. An element preceded by “a” or “an” does not,without further constraints, preclude the existence of additionalidentical elements in the process, method, article, or apparatus thatcomprises the element.

Unless otherwise stated, any and all measurements, values, ratings,positions, magnitudes, sizes, and other specifications that are setforth in this specification, including in the claims that follow, areapproximate, not exact. Such amounts are intended to have a reasonablerange that is consistent with the functions to which they relate andwith what is customary in the art to which they pertain. For example,unless expressly stated otherwise, a parameter value or the like mayvary by as much as plus or minus ten percent from the stated amount orrange.

In addition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in various examples for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimed examplesrequire more features than are expressly recited in each claim. Rather,as the following claims reflect, the subject matter to be protected liesin less than all features of any single disclosed example. Thus, thefollowing claims are hereby incorporated into the Detailed Description,with each claim standing on its own as a separately claimed subjectmatter.

While the foregoing has described what are considered to be the bestmode and other examples, it is understood that various modifications maybe made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that they may be appliedin numerous applications, only some of which have been described herein.It is intended by the following claims to claim any and allmodifications and variations that fall within the true scope of thepresent concepts.

1. Eyewear, comprising: a frame having a first side and a second side; afirst system on a chip (SoC) adjacent the first side of the frame, thefirst SoC coupled to first electronic components; a second SoC adjacentthe second side of the frame, the second SoC coupled to secondelectronic components; a universal serial bus (USB) port; a USB hubcoupled to the USB port, wherein the USB hub is configured to enable theUSB port to control each of the first and second SoCs; and a processorcoupled to the USB port and each of the first and second SoCs, theprocessor configured to enable the USB port to perform low-powerdebugging and automation of the first and second SoCs.
 2. (canceled) 3.The eyewear of claim 1, wherein the USB hub is disabled when the USBport is configured to perform low-power debugging and automation of thefirst and second SoCs.
 4. The eyewear of claim 1, wherein the USB portis configured to perform low-power debugging and automation using eithera Universal Asynchronous Receiver-Transmitter (UART) or a Serial WireDebug (SWD).
 5. The eyewear of claim 1, further comprising a firstswitch and a control logic, wherein the control logic is configured tocontrol the first switch and enable the USB port to perform low-powerdebugging and automation of the first and second SoCs via the processor.6. The eyewear of claim 5, further comprising a second switch, whereinthe control logic is configured to control the second switch to enablethe USB port to perform low-power debugging and automation of the firstand second SoCs via the processor, or to enable the USB port to controleach of the first and second SoCs.
 7. The eyewear of claim 5, whereinthe control logic is configured disable the USB hub such that the firstand second SoCs enter low-power modes without being kept awake by apersistent USB connection.
 8. The eyewear of claim 5, further comprisinga USB controller configured to provide a device test system (DTS)detection to the control logic to allow full recovery using the USBport.
 9. The eyewear of claim 5, wherein the first SoC is configured toenable the control logic to control the first switch and enable the USBport to perform low-power debugging and automation of the first andsecond SoCs via the processor.
 10. A method of using eyewear having aframe having a first side and a second side, a first system on a chip(SoC) adjacent the first side of the frame, the first SoC coupled tofirst electronic components, a second SoC adjacent the second side ofthe frame, the second SoC coupled to second electronic components, auniversal serial bus (USB) port, a USB hub coupled to the USB port, anda processor coupled to the USB port and each of the first and secondSoCs, comprising: configuring the USB port to control each of the firstand second SoCs; and the processor enabling the USB port to performlow-power debugging and automation of the first and second SoCs. 11.(canceled)
 12. The method of claim 10, further comprising disabling theUSB hub such that the USB port performs low-power debugging andautomation of the first and second SoCs.
 13. The method of claim 10,wherein the USB port performs low-power debugging and automation usingeither a Universal Asynchronous Receiver-Transmitter (UART) or a SerialWire Debug (SWD).
 14. The method of claim 10, wherein the eyewearfurther comprises a first switch and a control logic, wherein thecontrol logic controls the first switch and enables the USB port toperform low-power debugging and automation of the first and second SoCsvia the processor.
 15. The method of claim 14, wherein the eyewearfurther comprises a second switch, wherein the control logic controlsthe second switch to enable the USB port to perform low-power debuggingand automation of the first and second SoCs via the processor, or toenable the USB port to control each of the first and second SoCs. 16.The method of claim 14, wherein the control logic disables the USB hubsuch that the first and second SoCs enter low-power modes without beingkept awake by a persistent USB connection.
 17. The method of claim 14,wherein the eyewear further comprises a USB providing a device testsystem (DTS) detection to the control logic to allow full recovery usingthe USB port.
 18. The method of claim 14, wherein the first SoC enablesthe control logic to control the first switch and enable the USB port toperform low-power debugging and automation of the first and second SoCsvia the processor.
 19. A non-transitory computer-readable medium storingprogram code which, when executed by a processor of eyewear having aframe having a first side and a second side, a first system on a chip(SoC) adjacent the first side of the frame, the first SoC coupled tofirst electronic components, a second SoC adjacent the second side ofthe frame, the second SoC coupled to second electronic components, auniversal serial bus (USB) port, and a USB hub coupled to the USB port,is operative to cause a computing device to perform the steps of:configuring the USB port to control each of the first and second SoCs;enabling the USB port to perform low-power debugging and automation ofthe first and second SoCs; and controlling a first switch and enable theUSB port to perform low-power debugging and automation of the first andsecond SoCs, and controlling a second switch to enable the USB port toperform low-power debugging and automation of the first and second SoCs,or to enable the USB port to control each of the first and second SoCs.20. (canceled)